home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: dd.chalmers.se!news.chalmers.se!sunic!trane.uninett.no!eunet.no!EU.net!howland.reston.ans.net!vixen.cso.uiuc.edu!sdd.hp.com!nigel.msen.com!zib-berlin.de!news.belwue.de!news.uni-ulm.de!rz.uni-karlsruhe.de!stepsun.uni-kl.de!uklirb.informatik.uni-kl.de!feck
- From: feck@informatik.uni-kl.de (Christoph Feck IRZ)
- Subject: Re: amazing disappearing Write() s
- Message-ID: <1994Apr23.205258@informatik.uni-kl.de>
- Sender: news@uklirb.informatik.uni-kl.de (Unix-News-System)
- Nntp-Posting-Host: uklira.informatik.uni-kl.de
- Organization: University of Kaiserslautern, Germany
- References: <1994Apr22.172338.1@utxvms.cc.utexas.edu>
- Date: Sat, 23 Apr 1994 18:52:58 GMT
- Lines: 24
-
- In article <1994Apr22.172338.1@utxvms.cc.utexas.edu>, cbloom@utxvms.cc.utexas.edu writes:
- >
- > I have been writing a file-io intensive program (Open/Read/Write/Close) and
- > find an erratic/random problem: sometime the changes made by Write don't stay
- > made after a Close. The changes are in effect for subsequent reads in the
- > same run, but the changes suddenly disappear when the program compeletes!
- > Do I need to Flush() a file before closing it? Does anyone have any ideas?
-
- Close() does a Flush() itself. But you must Flush() if you change
- data transfer direction with buffered files (FRead/FWrite).
-
- > Also, there is an OpenFromLock() but no LockFromFH() - why not? Does Open()
-
- It's called DupLockFromFH(). The file will not be closed, unlike
- OpenFromLock() where the lock is released.
-
- > automatically Lock a file and Close UnLock() ? If so, is it always ACCESS_
- > WRITE ? How do you control it iit is automatic?
-
- It should be ACCESS_READ for MODE_OLD and ACCESS_WRITE otherwise.
- Ralph? :)
-
- 3k// Christoph Feck, TowerSystems - BOOPSI Class Development
- \X/ Amiga - Intuition inside.
-